#region (c) 2014 THN Solutions LLC. - All rights reserved
/*
Simplified BSD License (BSD)
THN HTTP Stack Library
Copyright (c) 2014, THN Solutions LLC. ( www.ThnSolutions.com )
Author: Nguyễn, M. Hải                 ( www.Minh-Hai.com     )
All rights reserved.

Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:

    * Redistributions of source code must retain the above copyright notice, this 
      list of conditions and the following disclaimer.

    * Redistributions in binary form must reproduce the above copyright notice, 
      this list of conditions and the following disclaimer in the documentation 
      and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
POSSIBILITY OF SUCH DAMAGE.
*/
#endregion

#region Record of Change
//             							CHANGE HISTORY
// -------------------------------------------------------------------------------------
// |   DATE    | DEVELOPER  | DESCRIPTION                                              |
// -------------------------------------------------------------------------------------
// | 04-Nov-11 | HaiNM      | First creation.                                          |
// -------------------------------------------------------------------------------------
//
#endregion

#region Record of Audit
//             							REVIEW HISTORY
// -------------------------------------------------------------------------------------
// |   DATE    | REVIEWER   | NOTES                                                    |
// -------------------------------------------------------------------------------------
// -------------------------------------------------------------------------------------
//
#endregion

#region Using directives
using System;

using Thn;
#endregion

namespace Thn.Net.Http
{
    /// <summary>
    /// Pre-defined status code of HTTP response according to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html .
    /// </summary>
#if DEBUG || TESTING
    public
#else
    public
#endif
 enum HttpResponseStatus
    {
        /// <summary>
        /// The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code.
        /// </summary>
        Continue = 100,
        /// <summary>
        /// The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
        /// </summary>
        SwitchingProtocol = 101,
        /// <summary>
        /// The request has succeeded. The information returned with the response is dependent on the method used in the request.
        /// </summary>
        OK = 200,
        /// <summary>
        /// The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field.
        /// </summary>
        Created = 201,
        /// <summary>
        /// The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.
        /// </summary>
        Accepted = 202,
        /// <summary>
        /// The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).
        /// </summary>
        NonAutoritativeInformation = 203,
        /// <summary>
        /// The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.
        /// </summary>
        NoContent = 204,
        /// <summary>
        /// The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.
        /// </summary>
        ResetContent = 205,
        /// <summary>
        /// The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field (section 14.35) indicating the desired range, and MAY have included an If-Range header field (section 14.27) to make the request conditional.
        /// </summary>
        PartialContent = 206,
        /// <summary>
        /// The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
        /// </summary>
        MultipleChoices = 300,
        /// <summary>
        /// The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
        /// </summary>
        MovedPermanently = 301,
        /// <summary>
        /// The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
        /// </summary>
        Found = 302,
        /// <summary>
        /// The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.
        /// </summary>
        SeeOther = 303,
        /// <summary>
        /// If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.
        /// </summary>
        NotModified = 304,
        /// <summary>
        /// The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers.
        /// </summary>
        UseProxy = 305,
        /// <summary>
        /// The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.
        /// </summary>
        Unused_306 = 306,
        /// <summary>
        /// The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
        /// </summary>
        TemporaryRedirect = 307,
        /// <summary>
        /// The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
        /// </summary>
        BadRequest = 400,
        /// <summary>
        /// The request requires user authentication.
        /// </summary>
        Unauthorized = 401,
        /// <summary>
        /// This code is reserved for future use.
        /// </summary>
        PaymentRequired = 402,
        /// <summary>
        /// The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
        /// </summary>
        Forbidden = 403,
        /// <summary>
        /// The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
        /// </summary>
        NotFound = 404,
        /// <summary>
        /// The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
        /// </summary>
        MethodNotAllowed = 405,
        /// <summary>
        /// The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
        /// </summary>
        NotAcceptable = 406,
        /// <summary>
        /// This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.
        /// </summary>
        ProxyAuthenticationRequired = 407,
        /// <summary>
        /// The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
        /// </summary>
        RequestTimeout = 408,
        /// <summary>
        /// The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request.
        /// </summary>
        Conflict = 409,
        /// <summary>
        /// The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent.
        /// </summary>
        Gone = 410,
        /// <summary>
        /// The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
        /// </summary>
        LengthRequired = 411,
        /// <summary>
        /// The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.
        /// </summary>
        PreconditionFailed = 412,
        /// <summary>
        /// The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
        /// </summary>
        RequestEntityTooLarge = 413,
        /// <summary>
        /// The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
        /// </summary>
        RequestUriTooLong = 414,
        /// <summary>
        /// The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
        /// </summary>
        UnsupportedMediaType = 415,
        /// <summary>
        /// A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)
        /// </summary>
        RequestedRangeNotStatisfiable = 416,
        /// <summary>
        /// The expectation given in an Expect request-header field (see section 14.20) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
        /// </summary>
        ExpectationFailed = 417,
        /// <summary>
        /// The server encountered an unexpected condition which prevented it from fulfilling the request.
        /// </summary>
        InternalServerError = 500,
        /// <summary>
        /// The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
        /// </summary>
        NotImplemented = 501,
        /// <summary>
        /// The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
        /// </summary>
        BadGateway = 502,
        /// <summary>
        /// The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
        /// </summary>
        ServiceUnavailable = 503,
        /// <summary>
        /// The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
        /// </summary>
        GatewayTimeout = 504,
        /// <summary>
        /// The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described in section 3.1, other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.
        /// </summary>
        HttpVersionNotSupported = 505,

    }
}
